VOCS APOSMM direct implementation - #1711

…s suggests. mypy fixes

…_cube

When using APOSMM with variables_mapping that includes x_on_cube, the
GenSpecs model's outputs field was being set from VOCS-derived variables
instead of from the APOSMM generator's gen_specs['out']. This caused
H['x_on_cube'] to be unavailable in the History array, leading to
ValueError: no field of name x_on_cube.

The fix moves the generator gen_specs['out'] check into set_fields_from_vocs
so it runs before the VOCS fallback.

The project() function was calling project_to_target_fidelity without
the required 'd' parameter (total input dimension), which is now a
required positional argument in botorch 0.17.2.

GITHUB_ENV is only set in GitHub Actions, not in local pixi environments.
Default to /dev/null when GITHUB_ENV is not set.

Previously, when using APOSMA with variables_mapping, the GenSpecs outputs
field was set from VOCS only, missing fields like x_on_cube, local_min, etc.
that are produced by the APOSMA generator. This caused tests to fail when
accessing H['x_on_cube'].

The fix merges the generator's gen_specs['out'] fields into the outputs
alongside the VOCS-derived fields, so the History array has all needed fields.